docs(publish): record the first Go SDK release (sdk/go/v0.1.0) - #72
Merged
Conversation
The tag is pushed on green main (4377bff) and the module is live: proxy.golang.org serves sdk/go v0.1.0 with a recorded sum.golang.org checksum, and the example provider built against the externally-fetched module passes all 13 conformance checks. verify-go (the only job an sdk/go/v* tag triggers) is green. - CHANGELOG: add the Go publish entry; all three SDKs and all three crates are now live. - sdk/PUBLISHING.md: flip the Go row to published; the file is now the checklist for subsequent releases. - sdk/go/README: drop the 'not yet published' caveat; pin the install snippet to @v0.1.0.
Reviewer's guide (collapsed on small PRs)Reviewer's GuideRecords and documents the first Go SDK publish (sdk/go/v0.1.0), updating changelog, publishing status table, and Go SDK README install instructions to reflect that the module is now published and pinned to v0.1.0. Flow diagram for Go SDK v0.1.0 publish and verificationflowchart TD
A[tag sdk/go/v0.1.0 on green main 4377bff3] --> B[go get github.com/macanderson/context-graph-protocol/sdk/go/contextgraph@v0.1.0]
B --> C[proxy.golang.org/sum.golang.org seeded]
C --> D[example provider build against external module]
D --> E[.github/scripts/conformance-external.sh passes 13 checks]
A --> F[verify-go GitHub job runs]
F --> G[verify-go green]
E --> H[All three SDKs and crates recorded as published in docs]
G --> H
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 1 issue
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="sdk/PUBLISHING.md" line_range="18-19" />
<code_context>
-**Nobody has run the Go publish steps yet.** This file exists so the
-*first* real publish of each is a checklist, not an improvisation — exactly
-the role [`../PUBLISHING.md`](../PUBLISHING.md) plays for the crates.
+**All three first publishes have now happened.** This file remains the
+checklist for every *subsequent* release, so a version bump is a checklist,
+not an improvisation — exactly the role
</code_context>
<issue_to_address>
**suggestion (typo):** Wording of “first publishes” is awkward; consider a more natural phrase.
“First publishes” is an unusual noun phrase. Please reword this sentence for clarity, e.g., “All three initial publishes have now happened,” “All three first publications have now happened,” or “All three first releases have now happened.”
```suggestion
**All three initial publishes have now happened.** This file remains the
checklist for every *subsequent* release, so a version bump is a checklist,
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Comment on lines
+18
to
+19
| **All three first publishes have now happened.** This file remains the | ||
| checklist for every *subsequent* release, so a version bump is a checklist, |
There was a problem hiding this comment.
suggestion (typo): Wording of “first publishes” is awkward; consider a more natural phrase.
“First publishes” is an unusual noun phrase. Please reword this sentence for clarity, e.g., “All three initial publishes have now happened,” “All three first publications have now happened,” or “All three first releases have now happened.”
Suggested change
| **All three first publishes have now happened.** This file remains the | |
| checklist for every *subsequent* release, so a version bump is a checklist, | |
| **All three initial publishes have now happened.** This file remains the | |
| checklist for every *subsequent* release, so a version bump is a checklist, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the Go SDK publish that just happened — the
sdk/go/v0.1.0tag is pushed on green main (4377bff3), which for a Go module is the publish.Verified before this PR:
proxy.golang.orgservesgithub.com/macanderson/context-graph-protocol/sdk/go v0.1.0— the firstgo getwas run deliberately to seed the proxy + checksum DB, per sdk/PUBLISHING.md's own recommendation, and a scratch module records thego.sumentry.conformance-external.sh— the P0: Publish the provider SDKs to PyPI and the Go module registry #59 acceptance bar, now met for all three SDKs.verify-go(the only job ansdk/go/v*tag can trigger — the publish-* jobs are dispatch-only) is green.Doc flips: CHANGELOG entry, sdk/PUBLISHING.md status table (all three SDKs ✅), sdk/go/README install snippet pinned to
@v0.1.0with the 'not yet published' caveat removed.Summary by Sourcery
Document the first Go SDK publish and update SDK publishing status across docs.
Documentation: